Skip to content

fix(benchmark): Keep run_command from exiting after success#540

Closed
Gujiassh wants to merge 1 commit into
microsoft:mainfrom
Gujiassh:fix/script-run-command-success-refresh-20260411
Closed

fix(benchmark): Keep run_command from exiting after success#540
Gujiassh wants to merge 1 commit into
microsoft:mainfrom
Gujiassh:fix/script-run-command-success-refresh-20260411

Conversation

@Gujiassh
Copy link
Copy Markdown

Summary

  • refresh the old utils/e2e_benchmark.py success-path fix onto current main
  • stop run_command(..., log_step=None) from treating successful subprocess runs as fatal exits
  • keep the focused regression coverage proving successful runs return normally while failures still log and exit as before

Validation

  • python3 -m py_compile utils/e2e_benchmark.py tests/test_e2e_benchmark_run_command.py
  • python3 -m unittest discover -s tests -p 'test_e2e_benchmark_run_command.py'

Only abort benchmark setup when a subprocess actually fails so successful benchmark invocations can proceed past the helper wrapper.

Ultraworked with [Sisyphus](https://github.com/code-yeongyu/oh-my-opencode)

Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai>
@Gujiassh
Copy link
Copy Markdown
Author

Closing this authored PR as part of a May 13, 2026 cleanup pass: it has had no status update for more than one month. I am clearing stale queue noise rather than asking maintainers to keep reviewing an old branch.

@Gujiassh Gujiassh closed this May 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant